Collision handling in new radio (NR)

ABSTRACT

Certain aspects of the present disclosure relate to methods and apparatus for collision handling in NR. In certain aspect, a method for use by a wireless communications device includes detecting a collision between resources allocated to different channels and initiating collision handling when processing the different channels based on the detection, wherein at least one of the detection or the processing is based on one or more characteristics of the different channels or the wireless device. In certain aspects, the one or more characteristics comprise at least one of one or more numerologies associated with at least one of the different channels, a modulation order of at least one of the different channels, coding rate of at least one of the different channels, or one or more capabilities of the wireless device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 62/457,762 entitled “COLLISION HANDLING IN NEW RADIO (NR),” whichwas filed Feb. 10, 2017. The aforementioned application is hereinincorporated by reference in its entirety.

FIELD

The present disclosure relates generally to communication systems, andmore particularly, to methods and apparatus relating to collisionhandling in New Radio (NR) application.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power). Examples of such multiple-access technologies includeLong Term Evolution (LTE) systems, code division multiple access (CDMA)systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems.

In some examples, a wireless multiple-access communication system mayinclude a number of base stations, each simultaneously supportingcommunication for multiple communication devices, otherwise known asuser equipment (UEs). In LTE or LTE-A network, a set of one or more basestations may define an eNodeB (eNB). In other examples (e.g., in a nextgeneration or 5G network), a wireless multiple access communicationsystem may include a number of distributed units (DUs) (e.g., edge units(EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs),transmission reception points (TRPs), etc.) in communication with anumber of central units (CUs) (e.g., central nodes (CNs), access nodecontrollers (ANCs), etc.), where a set of one or more distributed units,in communication with a central unit, may define an access node (e.g., anew radio base station (NR BS), a new radio node-B (NR NB), a networknode, 5G NB, eNB, etc.). A base station or DU may communicate with a setof UEs on downlink channels (e.g., for transmissions from a base stationor to a UE) and uplink channels (e.g., for transmissions from a UE to abase station or distributed unit).

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example of an emergingtelecommunication standard is new radio (NR), for example, 5G radioaccess. NR is a set of enhancements to the LTE mobile standardpromulgated by Third Generation Partnership Project (3GPP). It isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingOFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink(UL) as well as support beamforming, multiple-input multiple-output(MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues toincrease, there exists a desire for further improvements in NRtechnology. Preferably, these improvements should be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

BRIEF SUMMARY

The systems, methods, and devices of the disclosure each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure as expressedby the claims which follow, some features will now be discussed briefly.After considering this discussion, and particularly after reading thesection entitled “Detailed Description” one will understand how thefeatures of this disclosure provide advantages that include improvedcommunications between access points and stations in a wireless network.

Certain aspects provide a method for wireless communication by awireless device. The method generally includes detecting a collisionbetween resources allocated to different channels and initiatingcollision handling when processing the different channels based on thedetection, wherein at least one of the detection or the processing isbased on one or more characteristics of the different channels or thewireless device, and wherein the one or more characteristics comprise atleast one of one or more numerologies associated with at least one ofthe different channels, a modulation order of at least one of thedifferent channels, coding rate of at least one of the differentchannels, or one or more capabilities of the wireless device.

Certain aspects provide a method for wireless communication by awireless device. The method generally includes determining a size of aresource block group (RBG) based, at least in part, on a location of theRBG relative to at least one of a synchronization channel, a physicalbroadcast channel (PBCH), or bandwidth edge and determining allocatedresources based on the determined size.

Also described herein are embodiments of an apparatus for wirelesscommunications comprising means for detecting a collision betweenresources allocated to different channels and means for initiatingcollision handling when processing the different channels based on thedetection, wherein at least one of the detection or the processing isbased on one or more characteristics of the different channels or theapparatus, and wherein the one or more characteristics comprise at leastone of one or more numerologies associated with at least one of thedifferent channels, a modulation order of at least one of the differentchannels, coding rate of at least one of the different channels, or oneor more capabilities of the apparatus.

Also described herein are embodiments of an apparatus for wirelesscommunications comprising means for determining a size of a resourceblock group (RBG) based, at least in part, on a location of the RBGrelative to at least one of a synchronization channel, a physicalbroadcast channel (PBCH), or bandwidth edge and means for determiningallocated resources based on the determined size.

Aspects generally include methods, apparatus, systems, computer readablemediums, and processing systems, as substantially described herein withreference to and as illustrated by the accompanying drawings.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the appended drawings. It is to be noted,however, that the appended drawings illustrate only certain typicalaspects of this disclosure and are therefore not to be consideredlimiting of its scope, for the description may admit to other equallyeffective aspects.

FIG. 1 is a block diagram conceptually illustrating an exampletelecommunications system, in accordance with certain aspects of thepresent disclosure.

FIG. 2 is a block diagram illustrating an example logical architectureof a distributed RAN, in accordance with certain aspects of the presentdisclosure.

FIG. 3 is a diagram illustrating an example physical architecture of adistributed RAN, in accordance with certain aspects of the presentdisclosure.

FIG. 4 is a block diagram conceptually illustrating a design of anexample BS and user equipment (UE), in accordance with certain aspectsof the present disclosure.

FIG. 5 is a diagram showing examples for implementing a communicationprotocol stack, in accordance with certain aspects of the presentdisclosure.

FIG. 6 illustrates an example of a DL-centric subframe, in accordancewith certain aspects of the present disclosure.

FIG. 7 illustrates an example of an UL-centric subframe, in accordancewith certain aspects of the present disclosure.

FIG. 8 illustrates an example of a table showing various systembandwidths corresponding to various RBG sizes, in accordance withaspects of the present disclosure.

FIG. 9 illustrates example operations for handling collisions in NR, inaccordance with aspects of the present disclosure.

FIG. 10 illustrates other example operations for handling collisions inNR, in accordance with aspects of the present disclosure.

FIG. 11 illustrates an example of numerology dependency relating tohandling NR PDSCH/PDCCH (physical downlink shared channel/physicaldownlink control channel) collisions with NR PSS/SSS/PBCH (primarysynchronization signal/secondary synchronization signal/physicalbroadcast channel), in accordance with aspects of the presentdisclosure.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in one aspectmay be beneficially utilized on other aspects without specificrecitation.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatus, methods, processingsystems, and computer readable mediums for new radio (NR) (e.g., newradio access technology or 5G technology). In particular, certainaspects of the present disclosure relate to collision handling in NR.Collision handling generally refers to actions taken when one or moreportions of resources assigned to different channels overlap.

NR may support various wireless communication services, such as Enhancedmobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond),millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz),massive MTC (mMTC) targeting non-backward compatible MTC techniques,and/or mission critical targeting ultra-reliable low latencycommunications (URLLC). These services may include latency andreliability requirements. These services may also have differenttransmission time intervals (TTI) to meet respective quality of service(QoS) requirements. In addition, these services may co-exist in the samesubframe.

As described below, to assist UE 120 with cell search, BS 110 maytransmit two special signals, the Primary Synchronization Signal (PSS)and the Secondary Synchronization Signal (SSS), on each downlinkcomponent carrier. In some cases, resources for PSS/SSS/PBCH may collidewith the physical downlink shared channel and the physical downlinkshared channel resources. Although under LTE there are agreed-tostandards for handling such collisions, the design of PSS, SSS, and alsophysical broadcast channel (PBCH) is a work in progress under the NR/5gstandards and may differ from the design of PSS/SSS/PBCH under the LTEstandards. For example, in some cases, under the NR standards,PSS/SSS/PBCH may have a different bandwidth than that of LTE, which hasa bandwidth of about 1.08 MHz. In addition, in some cases, under the NRstandards, PSS/SSS/PBCH may not be centered. Also, in some cases,PSS/SSS/PBCH may have a different numerology under NR (e.g. a referencenumerology, for example, like tone spacing) than under LTE (e.g., 30 kHzin NR vs. 15 kHz in LTE). Accordingly, certain embodiments discussedherein are directed to handling NR PDSCH/PDCCH collision with NRPSS/SSS/PBCH considering that, first, NR PDSCH/PDCCH may have differentnumerology than NR PSS/SSS/PBCH and, second, DM-RS for NR PDSCH/PDCCHmay be front-loaded and thus may not collide with NR PSS/SSS/PBCH. Inaddition, some embodiments discussed herein are directed to handlingpotential interfaces in uplink transmissions, considering NR PUCCH andNR PUSCH may have different numerologies.

The following description provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the methods described may be performed in an order differentfrom that described, and various steps may be added, omitted, orcombined. Also, features described with respect to some examples may becombined in some other examples. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect of the disclosure disclosed hereinmay be embodied by one or more elements of a claim. The word “exemplary”is used herein to mean “serving as an example, instance, orillustration.” Any aspect described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otheraspects.

The techniques described herein may be used for various wirelesscommunication networks such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA andother networks. The terms “network” and “system” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. cdma2000 coversIS-2000, IS-95 and IS-856 standards. A TDMA network may implement aradio technology such as Global System for Mobile Communications (GSM).An OFDMA network may implement a radio technology such as NR (e.g. 5GRA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA andE-UTRA are part of Universal Mobile Telecommunication System (UMTS). NRis an emerging wireless communications technology under development inconjunction with the 5G Technology Forum (5GTF). 3GPP Long TermEvolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that useE-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described indocuments from an organization named “3rd Generation PartnershipProject” (3GPP). cdma2000 and UMB are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). Thetechniques described herein may be used for the wireless networks andradio technologies mentioned above as well as other wireless networksand radio technologies. For clarity, while aspects may be describedherein using terminology commonly associated with 3G and/or 4G wirelesstechnologies, aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

Example Wireless Communications System

FIG. 1 illustrates an example wireless network 100, such as a new radio(NR) or 5G network, in which aspects of the present disclosure may beperformed.

As illustrated in FIG. 1, the wireless network 100 may include a numberof BSs 110 and other network entities. A BS may be a station thatcommunicates with UEs. Each BS 110 may provide communication coveragefor a particular geographic area. In 3GPP, the term “cell” can refer toa coverage area of a Node B and/or a Node B subsystem serving thiscoverage area, depending on the context in which the term is used. In NRsystems, the term “cell” and eNB, Node B, 5G NB, AP, NR BS, NR BS, nextgeneration NodeB (gNB), or TRP may be interchangeable. In some examples,a cell may not necessarily be stationary, and the geographic area of thecell may move according to the location of a mobile base station. Insome examples, the base stations may be interconnected to one anotherand/or to one or more other base stations or network nodes (not shown)in the wireless network 100 through various types of backhaul interfacessuch as a direct physical connection, a virtual network, or the likeusing any suitable transport network.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies. ARAT may also be referred to as a radio technology, an air interface,etc. A frequency may also be referred to as a carrier, a frequencychannel, etc. Each frequency may support a single RAT in a givengeographic area in order to avoid interference between wireless networksof different RATs. In some cases, NR or 5G RAT networks may be deployed.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or other types of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a Closed Subscriber Group (CSG), UEs for users in the home,etc.). A BS for a macro cell may be referred to as a macro BS. A BS fora pico cell may be referred to as a pico BS. A BS for a femto cell maybe referred to as a femto BS or a home BS. In the example shown in FIG.1, the BSs 110 a, 110 b and 110 c may be macro BSs for the macro cells102 a, 102 b and 102 c, respectively. The BS 110 x may be a pico BS fora pico cell 102 x. The BSs 110 y and 110 z may be femto BS for the femtocells 102 y and 102 z, respectively. A BS may support one or multiple(e.g., three) cells.

The wireless network 100 may also include relay stations. A relaystation is a station that receives a transmission of data and/or otherinformation from an upstream station (e.g., a BS or a UE) and sends atransmission of the data and/or other information to a downstreamstation (e.g., a UE or a BS). A relay station may also be a UE thatrelays transmissions for other UEs. In the example shown in FIG. 1, arelay station 110 r may communicate with the BS 110 a and a UE 120 r inorder to facilitate communication between the BS 110 a and the UE 120 r.A relay station may also be referred to as a relay BS, a relay, etc.

The wireless network 100 may be a heterogeneous network that includesBSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc.These different types of BSs may have different transmit power levels,different coverage areas, and different impact on interference in thewireless network 100. For example, macro BS may have a high transmitpower level (e.g., 20 Watts) whereas pico BS, femto BS, and relays mayhave a lower transmit power level (e.g., 1 Watt).

The wireless network 100 may support synchronous or asynchronousoperation. For synchronous operation, the BSs may have similar frametiming, and transmissions from different BSs may be approximatelyaligned in time. For asynchronous operation, the BSs may have differentframe timing, and transmissions from different BSs may not be aligned intime. The techniques described herein may be used for both synchronousand asynchronous operation.

A network controller 130 may be coupled to a set of BSs and providecoordination and control for these BSs. The network controller 130 maycommunicate with the BSs 110 via a backhaul. The BSs 110 may alsocommunicate with one another, e.g., directly or indirectly via wirelessor wireline backhaul.

The UEs 120 (e.g., 120 x, 120 y, etc.) may be dispersed throughout thewireless network 100, and each UE may be stationary or mobile. A UE mayalso be referred to as a mobile station, a terminal, an access terminal,a subscriber unit, a station, a Customer Premises Equipment (CPE), acellular phone, a smart phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, alaptop computer, a cordless phone, a wireless local loop (WLL) station,a tablet, a camera, a gaming device, a netbook, a smartbook, anultrabook, a medical device or medical equipment, a biometricsensor/device, a wearable device such as a smart watch, smart clothing,smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, asmart bracelet, etc.), an entertainment device (e.g., a music device, avideo device, a satellite radio, etc.), a vehicular component or sensor,a smart meter/sensor, industrial manufacturing equipment, a globalpositioning system device, or any other suitable device that isconfigured to communicate via a wireless or wired medium. Some UEs maybe considered evolved or machine-type communication (MTC) devices orevolved MTC (eMTC) devices. MTC and eMTC UEs include, for example,robots, drones, remote devices, sensors, meters, monitors, locationtags, etc., that may communicate with a BS, another device (e.g., remotedevice), or some other entity. A wireless node may provide, for example,connectivity for or to a network (e.g., a wide area network such asInternet or a cellular network) via a wired or wireless communicationlink. Some UEs may be considered Internet-of-Things (IoT) devices.

In FIG. 1, a solid line with double arrows indicates desiredtransmissions between a UE and a serving BS, which is a BS designated toserve the UE on the downlink and/or uplink. A dashed line with doublearrows indicates interfering transmissions between a UE and a BS.

Certain wireless networks (e.g., LTE) utilize orthogonal frequencydivision multiplexing (OFDM) on the downlink and single-carrierfrequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDMpartition the system bandwidth into multiple (K) orthogonal subcarriers,which are also commonly referred to as tones, bins, etc. Each subcarriermay be modulated with data. In general, modulation symbols are sent inthe frequency domain with OFDM and in the time domain with SC-FDM. Thespacing between adjacent subcarriers may be fixed, and the total numberof subcarriers (K) may be dependent on the system bandwidth. Forexample, the spacing of the subcarriers may be 15 kHz and the minimumresource allocation (called a ‘resource block’) may be 12 subcarriers(or 180 kHz). Consequently, the nominal FFT size may be equal to 128,256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20megahertz (MHz), respectively. The system bandwidth may also bepartitioned into subbands. For example, a subband may cover 1.08 MHz(i.e., 6 resource blocks), and there may be 1, 2, 4, 8 or 16 subbandsfor system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.

While aspects of the examples described herein may be associated withLTE technologies, aspects of the present disclosure may be applicablewith other wireless communications systems, such as NR. NR may utilizeOFDM with a CP on the uplink and downlink and include support forhalf-duplex operation using time division duplex (TDD). A singlecomponent carrier bandwidth of 100 MHz may be supported. NR resourceblocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHzover a 0.1 ms duration. Each radio frame may consist of 50 subframeswith a length of 10 ms. Consequently, each subframe may have a length of0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) fordata transmission and the link direction for each subframe may bedynamically switched. Each subframe may include DL/UL data as well asDL/UL control data. UL and DL subframes for NR may be as described inmore detail below with respect to FIGS. 6 and 7. Beamforming may besupported and beam direction may be dynamically configured. MIMOtransmissions with precoding may also be supported. MIMO configurationsin the DL may support up to 8 transmit antennas with multi-layer DLtransmissions up to 8 streams and up to 2 streams per UE. Multi-layertransmissions with up to 2 streams per UE may be supported. Aggregationof multiple cells may be supported with up to 8 serving cells.Alternatively, NR may support a different air interface, other than anOFDM-based. NR networks may include entities such CUs and/or DUs.

In some examples, access to the air interface may be scheduled, whereina scheduling entity (e.g., a base station) allocates resources forcommunication among some or all devices and equipment within its servicearea or cell. Within the present disclosure, as discussed further below,the scheduling entity may be responsible for scheduling, assigning,reconfiguring, and releasing resources for one or more subordinateentities. That is, for scheduled communication, subordinate entitiesutilize resources allocated by the scheduling entity. Base stations arenot the only entities that may function as a scheduling entity. That is,in some examples, a UE may function as a scheduling entity, schedulingresources for one or more subordinate entities (e.g., one or more otherUEs). In this example, the UE is functioning as a scheduling entity, andother UEs utilize resources scheduled by the UE for wirelesscommunication. A UE may function as a scheduling entity in apeer-to-peer (P2P) network, and/or in a mesh network. In a mesh networkexample, UEs may optionally communicate directly with one another inaddition to communicating with the scheduling entity.

Thus, in a wireless communication network with a scheduled access totime-frequency resources and having a cellular configuration, a P2Pconfiguration, and a mesh configuration, a scheduling entity and one ormore subordinate entities may communicate utilizing the scheduledresources.

As noted above, a RAN may include a CU and DUs. A NR BS (e.g., eNB, 5GNode B, Node B, transmission reception point (TRP), access point (AP))may correspond to one or multiple BSs. NR cells can be configured asaccess cell (ACells) or data only cells (DCells). For example, the RAN(e.g., a central unit or distributed unit) can configure the cells.DCells may be cells used for carrier aggregation or dual connectivity,but not used for initial access, cell selection/reselection, orhandover. In some cases DCells may not transmit synchronizationsignals—in some case cases DCells may transmit SS. NR BSs may transmitdownlink signals to UEs indicating the cell type. Based on the cell typeindication, the UE may communicate with the NR BS. For example, the UEmay determine NR BSs to consider for cell selection, access, handover,and/or measurement based on the indicated cell type.

FIG. 2 illustrates an example logical architecture of a distributedradio access network (RAN) 200, which may be implemented in the wirelesscommunication system illustrated in FIG. 1. A 5G access node 206 mayinclude an access node controller (ANC) 202. The ANC may be a centralunit (CU) of the distributed RAN 200. The backhaul interface to the nextgeneration core network (NG-CN) 204 may terminate at the ANC. Thebackhaul interface to neighboring next generation access nodes (NG-ANs)may terminate at the ANC. The ANC may include one or more TRPs 208(which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, orsome other term). As described above, a TRP may be used interchangeablywith “cell.”

The TRPs 208 may be a DU. The TRPs may be connected to one ANC (ANC 202)or more than one ANC (not illustrated). For example, for RAN sharing,radio as a service (RaaS), and service specific AND deployments, the TRPmay be connected to more than one ANC. A TRP may include one or moreantenna ports. The TRPs may be configured to individually (e.g., dynamicselection) or jointly (e.g., joint transmission) serve traffic to a UE.

The local architecture 200 may be used to illustrate fronthauldefinition. The architecture may be defined that support fronthaulingsolutions across different deployment types. For example, thearchitecture may be based on transmit network capabilities (e.g.,bandwidth, latency, and/or jitter).

The architecture may share features and/or components with LTE.According to aspects, the next generation AN (NG-AN) 210 may supportdual connectivity with NR. The NG-AN may share a common fronthaul forLTE and NR.

The architecture may enable cooperation between and among TRPs 208. Forexample, cooperation may be preset within a TRP and/or across TRPs viathe ANC 202. According to aspects, no inter-TRP interface may beneeded/present.

According to aspects, a dynamic configuration of split logical functionsmay be present within the architecture 200. As will be described in moredetail with reference to FIG. 5, the Radio Resource Control (RRC) layer,Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC)layer, Medium Access Control (MAC) layer, and a Physical (PHY) layersmay be adaptably placed at the DU or CU (e.g., TRP or ANC,respectively). According to certain aspects, a BS may include a centralunit (CU) (e.g., ANC 202) and/or one or more distributed units (e.g.,one or more TRPs 208).

FIG. 3 illustrates an example physical architecture of a distributed RAN300, according to aspects of the present disclosure. A centralized corenetwork unit (C-CU) 302 may host core network functions. The C-CU may becentrally deployed. C-CU functionality may be offloaded (e.g., toadvanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 304 may host one or more ANC functions.Optionally, the C-RU may host core network functions locally. The C-RUmay have distributed deployment. The C-RU may be closer to the networkedge.

A DU 306 may host one or more TRPs (edge node (EN), an edge unit (EU), aradio head (RH), a smart radio head (SRH), or the like). The DU may belocated at edges of the network with radio frequency (RF) functionality.

FIG. 4 illustrates example components of the BS 110 and UE 120illustrated in FIG. 1, which may be used to implement aspects of thepresent disclosure. As described above, the BS may include a TRP. One ormore components of the BS 110 and UE 120 may be used to practice aspectsof the present disclosure. For example, antennas 452, Tx/Rx 222,processors 466, 458, 464, and/or controller/processor 480 of the UE 120and/or antennas 434, processors 460, 420, 438, and/orcontroller/processor 440 of the BS 110 may be used to perform theoperations described herein and illustrated with reference to FIGS. 8and 9.

FIG. 4 shows a block diagram of a design of a BS 110 and a UE 120, whichmay be one of the BSs and one of the UEs in FIG. 1. For a restrictedassociation scenario, the base station 110 may be the macro BS 110 c inFIG. 1, and the UE 120 may be the UE 120 y. The base station 110 mayalso be a base station of some other type. The base station 110 may beequipped with antennas 434 a through 434 t, and the UE 120 may beequipped with antennas 452 a through 452 r.

At the base station 110, a transmit processor 420 may receive data froma data source 412 and control information from a controller/processor440. The control information may be for the Physical Broadcast Channel(PBCH), Physical Control Format Indicator Channel (PCFICH), PhysicalHybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel(PDCCH), etc. The data may be for the Physical Downlink Shared Channel(PDSCH), etc. The processor 420 may process (e.g., encode and symbolmap) the data and control information to obtain data symbols and controlsymbols, respectively. The processor 420 may also generate referencesymbols, e.g., for the PSS, SSS, and cell-specific reference signal. Atransmit (TX) multiple-input multiple-output (MIMO) processor 430 mayperform spatial processing (e.g., precoding) on the data symbols, thecontrol symbols, and/or the reference symbols, if applicable, and mayprovide output symbol streams to the modulators (MODs) 432 a through 432t. For example, the TX MIMO processor 430 may perform certain aspectsdescribed herein for RS multiplexing. Each modulator 432 may process arespective output symbol stream (e.g., for OFDM, etc.) to obtain anoutput sample stream. Each modulator 432 may further process (e.g.,convert to analog, amplify, filter, and upconvert) the output samplestream to obtain a downlink signal. Downlink signals from modulators 432a through 432 t may be transmitted via the antennas 434 a through 434 t,respectively.

At the UE 120, the antennas 452 a through 452 r may receive the downlinksignals from the base station 110 and may provide received signals tothe demodulators (DEMODs) 454 a through 454 r, respectively. Eachdemodulator 454 may condition (e.g., filter, amplify, downconvert, anddigitize) a respective received signal to obtain input samples. Eachdemodulator 454 may further process the input samples (e.g., for OFDM,etc.) to obtain received symbols. A MIMO detector 456 may obtainreceived symbols from all the demodulators 454 a through 454 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. For example, MIMO detector 456 may provide detected RStransmitted using techniques described herein. A receive processor 458may process (e.g., demodulate, deinterleave, and decode) the detectedsymbols, provide decoded data for the UE 120 to a data sink 460, andprovide decoded control information to a controller/processor 480.According to one or more cases, CoMP aspects can include providing theantennas, as well as some Tx/Rx functionalities, such that they residein distributed units. For example, some Tx/Rx processings can be done inthe central unit, while other processing can be done at the distributedunits. For example, in accordance with one or more aspects as shown inthe diagram, the BS mod/demod 432 may be in the distributed units.

On the uplink, at the UE 120, a transmit processor 464 may receive andprocess data (e.g., for the Physical Uplink Shared Channel (PUSCH)) froma data source 462 and control information (e.g., for the Physical UplinkControl Channel (PUCCH) from the controller/processor 480. The transmitprocessor 464 may also generate reference symbols for a referencesignal. The symbols from the transmit processor 464 may be precoded by aTX MIMO processor 466 if applicable, further processed by thedemodulators 454 a through 454 r (e.g., for SC-FDM, etc.), andtransmitted to the base station 110. At the BS 110, the uplink signalsfrom the UE 120 may be received by the antennas 434, processed by themodulators 432, detected by a MIMO detector 436 if applicable, andfurther processed by a receive processor 438 to obtain decoded data andcontrol information sent by the UE 120. The receive processor 438 mayprovide the decoded data to a data sink 439 and the decoded controlinformation to the controller/processor 440.

The controllers/processors 440 and 480 may direct the operation at thebase station 110 and the UE 120, respectively. The processor 440 and/orother processors and modules at the base station 110 may perform ordirect, e.g., the execution of the functional blocks illustrated inFIGS. 8 and 9, and/or other processes for the techniques describedherein. The processor 480 and/or other processors and modules at the UE120 may also perform or direct processes for the techniques describedherein. The memories 442 and 482 may store data and program codes forthe BS 110 and the UE 120, respectively. A scheduler 444 may scheduleUEs for data transmission on the downlink and/or uplink.

FIG. 5 illustrates a diagram 500 showing examples for implementing acommunications protocol stack, according to aspects of the presentdisclosure. The illustrated communications protocol stacks may beimplemented by devices operating in a in a 5G system (e.g., a systemthat supports uplink-based mobility). Diagram 500 illustrates acommunications protocol stack including a Radio Resource Control (RRC)layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a RadioLink Control (RLC) layer 520, a Medium Access Control (MAC) layer 525,and a Physical (PHY) layer 530. In various examples the layers of aprotocol stack may be implemented as separate modules of software,portions of a processor or ASIC, portions of non-collocated devicesconnected by a communications link, or various combinations thereof.Collocated and non-collocated implementations may be used, for example,in a protocol stack for a network access device (e.g., ANs, CUs, and/orDUs) or a UE.

A first option 505-a shows a split implementation of a protocol stack,in which implementation of the protocol stack is split between acentralized network access device (e.g., an ANC 202 in FIG. 2) anddistributed network access device (e.g., DU 208 in FIG. 2). In the firstoption 505-a, an RRC layer 510 and a PDCP layer 515 may be implementedby the central unit, and an RLC layer 520, a MAC layer 525, and a PHYlayer 530 may be implemented by the DU. In various examples the CU andthe DU may be collocated or non-collocated. The first option 505-a maybe useful in a macro cell, micro cell, or pico cell deployment.

A second option 505-b shows a unified implementation of a protocolstack, in which the protocol stack is implemented in a single networkaccess device (e.g., access node (AN), new radio base station (NR BS), anew radio Node-B (NR NB), a network node (NN), or the like.). In thesecond option, the RRC layer 510, the PDCP layer 515, the RLC layer 520,the MAC layer 525, and the PHY layer 530 may each be implemented by theAN. The second option 505-b may be useful in a femto cell deployment.

Regardless of whether a network access device implements part or all ofa protocol stack, a UE may implement an entire protocol stack (e.g., theRRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525,and the PHY layer 530).

FIG. 6 is a diagram 600 showing an example of a DL-centric subframe. TheDL-centric subframe may include a control portion 602. The controlportion 602 may exist in the initial or beginning portion of theDL-centric subframe. The control portion 602 may include variousscheduling information and/or control information corresponding tovarious portions of the DL-centric subframe. In some configurations, thecontrol portion 602 may be a physical DL control channel (PDCCH), asindicated in FIG. 6. The DL-centric subframe may also include a DL dataportion 604. The DL data portion 604 may sometimes be referred to as thepayload of the DL-centric subframe. The DL data portion 604 may includethe communication resources utilized to communicate DL data from thescheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE).In some configurations, the DL data portion 604 may be a physical DLshared channel (PDSCH).

The DL-centric subframe may also include a common UL portion 606. Thecommon UL portion 606 may sometimes be referred to as an UL burst, acommon UL burst, and/or various other suitable terms. The common ULportion 606 may include feedback information corresponding to variousother portions of the DL-centric subframe. For example, the common ULportion 606 may include feedback information corresponding to thecontrol portion 602. Non-limiting examples of feedback information mayinclude an ACK signal, a NACK signal, a HARQ indicator, and/or variousother suitable types of information. The common UL portion 606 mayinclude additional or alternative information, such as informationpertaining to random access channel (RACH) procedures, schedulingrequests (SRs), and various other suitable types of information. Asillustrated in FIG. 6, the end of the DL data portion 604 may beseparated in time from the beginning of the common UL portion 606. Thistime separation may sometimes be referred to as a gap, a guard period, aguard interval, and/or various other suitable terms. This separationprovides time for the switch-over from DL communication (e.g., receptionoperation by the subordinate entity (e.g., UE)) to UL communication(e.g., transmission by the subordinate entity (e.g., UE)). One ofordinary skill in the art will understand that the foregoing is merelyone example of a DL-centric subframe and alternative structures havingsimilar features may exist without necessarily deviating from theaspects described herein.

FIG. 7 is a diagram 700 showing an example of an UL-centric subframe.The UL-centric subframe may include a control portion 702. The controlportion 702 may exist in the initial or beginning portion of theUL-centric subframe. The control portion 702 in FIG. 7 may be similar tothe control portion described above with reference to FIG. 6. TheUL-centric subframe may also include an UL data portion 704. The UL dataportion 704 may sometimes be referred to as the payload of theUL-centric subframe. The UL data portion may refer to the communicationresources utilized to communicate UL data from the subordinate entity(e.g., UE) to the scheduling entity (e.g., UE or BS). In someconfigurations, the control portion 702 may be a physical DL controlchannel (PDCCH).

As illustrated in FIG. 7, the end of the control portion 702 may beseparated in time from the beginning of the UL data portion 704. Thistime separation may sometimes be referred to as a gap, guard period,guard interval, and/or various other suitable terms. This separationprovides time for the switch-over from DL communication (e.g., receptionoperation by the scheduling entity) to UL communication (e.g.,transmission by the scheduling entity). The UL-centric subframe may alsoinclude a common UL portion 706. The common UL portion 706 in FIG. 7 maybe similar to the common UL portion 706 described above with referenceto FIG. 7. The common UL portion 706 may additionally or alternativelyinclude information pertaining to channel quality indicator (CQI),sounding reference signals (SRSs), and various other suitable types ofinformation. One of ordinary skill in the art will understand that theforegoing is merely one example of an UL-centric subframe andalternative structures having similar features may exist withoutnecessarily deviating from the aspects described herein.

In some circumstances, two or more subordinate entities (e.g., UEs) maycommunicate with each other using sidelink signals. Real-worldapplications of such sidelink communications may include public safety,proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V)communications, Internet of Everything (IoE) communications, IoTcommunications, mission-critical mesh, and/or various other suitableapplications. Generally, a sidelink signal may refer to a signalcommunicated from one subordinate entity (e.g., UE1) to anothersubordinate entity (e.g., UE2) without relaying that communicationthrough the scheduling entity (e.g., UE or BS), even though thescheduling entity may be utilized for scheduling and/or controlpurposes. In some examples, the sidelink signals may be communicatedusing a licensed spectrum (unlike wireless local area networks, whichtypically use an unlicensed spectrum).

A UE may operate in various radio resource configurations, including aconfiguration associated with transmitting pilots using a dedicated setof resources (e.g., a radio resource control (RRC) dedicated state,etc.) or a configuration associated with transmitting pilots using acommon set of resources (e.g., an RRC common state, etc.). Whenoperating in the RRC dedicated state, the UE may select a dedicated setof resources for transmitting a pilot signal to a network. Whenoperating in the RRC common state, the UE may select a common set ofresources for transmitting a pilot signal to the network. In eithercase, a pilot signal transmitted by the UE may be received by one ormore network access devices, such as an AN, or a DU, or portionsthereof. Each receiving network access device may be configured toreceive and measure pilot signals transmitted on the common set ofresources, and also receive and measure pilot signals transmitted ondedicated sets of resources allocated to the UEs for which the networkaccess device is a member of a monitoring set of network access devicesfor the UE. One or more of the receiving network access devices, or a CUto which receiving network access device(s) transmit the measurements ofthe pilot signals, may use the measurements to identify serving cellsfor the UEs, or to initiate a change of serving cell for one or more ofthe UEs.

Example Collision Handling in NR

Aspects of the present application describe techniques for collisionhandling in NR. As used herein, the term collision generally refers toresources of two different channels overlapping or potentiallyoverlapping. A collision may be declared and considered detected whensignals transmitted on those different channels collide or when theresources (e.g., resource elements, resource blocks, etc.) allocated tothe two different channels overlap or potentially overlap (e.g.,resources of NR PSS/SSS/PBCH overlapping or potentially overlapping withresources of PDSCH/PDCCH, shown in FIG. 11). A potential overlap, forexample, may occur in cases in which resources allocated to the twodifferent channels do not actually overlap but may be within somefrequency gap (e.g., Δf) of each other. Upon detecting a collision, awireless device initiates collision handling, which, as used herein,includes any suitable collision handling technique such as skipping theprocessing of certain resources (e.g., RBs) or performing rate matching,etc.

To assist a user equipment (e.g., UE 120) with cell search, a basestation (e.g., BS 110) transmits two special signals, the PrimarySynchronization Signal (PSS) and the Secondary Synchronization Signal(SSS), on each downlink component carrier. In some cases, under the LTEstandards, PSS and SSS (“PSS/SSS”) may be transmitted in subframes 0 and5 of every frame (i.e., 10 subframes), while the physical broadcastchannel (PBCH) may be transmitted in subframes 0 of every frame. In somecases, PSS/SSS/PBCH may have a 6-RB (resource block) bandwidth, locatedin the center of the downlink (DL) system bandwidth. DL bandwidth may be6-RB, 15-RB, 25-RB, 50-RB, 75-RB and 100-RB in LTE.

In some cases, collision of a physical downlink shared channel (PDSCH)resource allocation with PSS/SSS/PBCH in a DL data transmission may bedealt with based on whether the PDSCH is cell-specific reference signal(CRS)-based or demodulation reference signal (DM-RS)-based. ForCRS-based PDSCH, the PDSCH rate may match around the resource elements(REs) occupied by PSS/SSS/PBCH. For DM-RS-based PDSCH, the collision maybe treated differently under the early release of LTE and Rel-13. Underthe early release of LTE, DM-RS-based PDSCH resource allocation may bedeemed as an error event causing the entire PDSCH to be skipped forprocessing. However, under Rel-13, if PDSCH partially collides withPSS/SSS/PBCH, PDSCH may still be required to be processed by the UE. Asa result, PDSCH rate may match around the RBs occupied by PSS/SSS/PBCH.Such a treatment may be useful considering that PDSCH resourceallocation, in some cases, may have a granularity of multiple physicalresource blocks (PRBs) (RB group, or resource block group (RBG)), suchthat it may be difficult to completely avoid collision with PSS/SSS/PBCHwhile maximizing resource allocation for PDSCH for a UE. Theabove-described processing may be inefficient.

In some cases, the RBG-based resource allocation for PDSCH may have twotypes, type 0 and type 1. The RBG size may be a function of DL systembandwidth. FIG. 8 illustrates a table containing a number of DL systembandwidth ranges, each range corresponding to a certain RBG size. Forexample, as shown in FIG. 8, the DL system bandwidth may be 20 MHz whenRBG is 4 RBs. In such an example, PSS/SSS/PBCH may be located in thecenter of 6 RBs (e.g. RBs 47, 48, 49, 50, 51, and 52). In addition, atype 0 PDSCH resource allocation may use a 25-bit bitmap, eachindicating a particular RBG (e.g. RBG0: RBs 0-3; RBG1: RBs 4-7; . . . ;RBG24: RBs 96-99). In some cases, in order to use RBs 44/45/46, the UEmay have to be assigned RBG 11 (RBs 44-47), which may partially collidesPSS/SSS/PBCH. Prior to Release 13, under the early release of LTE, ifthe UE is assigned RBG 11 for a DM-RS-based PDSCH, the entire PDSCH maybe skipped. However, under Rel-13 and later developments, PDSCH maystill be required to be processed, although RB 47 may be skipped forPDSCH rate matching, which is inefficient.

In some cases, in LTE, DM-RS-based enhanced physical downlink controlchannel (EPDCCH) may also collide with PSS/SSS/PBCH. If any EPDCCHdecoding candidate for a UE has an overlap, even partially, withPSS/SSS/PBCH, the decoding candidate may be skipped for decoding by theUE, which may be inefficient.

Unlike the PSS/SSS/PBCH design described above in relation to the LTEstandards, the PSS/SSS/PBCH design is a work in progress under the NR/5Gstandards as of the time of this filing. In some cases, under the NRstandards, PSS/SSS/PBCH may have a different bandwidth than that of LTE,which has a bandwidth of about 1.08 MHz. In addition, in some cases,under the NR standards, PSS/SSS/PBCH may not be centered. Also, in somecases, PSS/SSS/PBCH may have a different numerology under NR (e.g. areference numerology, for example, like tone spacing) than under LTE(e.g., 30 kHz in NR vs. 15 kHz in LTE).

Further, for NR PDSCH, the numerology can be flexible (e.g. 15 kHz/30kHz/60 kHz/120 kHz). Resource allocation for NR PDSCH may have agranularity of multiple RBs at least in some cases. In some cases, theNR DL bandwidth may be very wide (e.g., up to 1 GHz). As a result, amulti-RB granularity, similar to RBG in LTE, may be introduced in NR, tostrike a balance between control overhead and resource allocationgranularity. Therefore, to rely on implementation to completely avoid NRPSS/SSS/PBCH while achieving full-resource-utilization for PDSCH may notbe likely.

Accordingly, certain embodiments discussed herein are directed tohandling NR PDSCH/PDCCH collision with NR PSS/SSS/PBCH considering that,first, NR PDSCH/PDCCH may have different numerology than NR PSS/SSS/PBCHand, second, DM-RS for NR PDSCH/PDCCH may be front-loaded and thus maynot collide with NR PSS/SSS/PBCH. In addition, some embodimentsdiscussed herein are directed to handling potential interference inuplink transmissions, considering NR PUCCH and NR PUSCH may havedifferent numerologies.

FIG. 9 illustrates example operations 900 relating to collision handlingin NR, according to aspects of the present disclosure. Operations 900may be performed, for example, by a UE or a base station.

Operations 900 begin, at 902, by detecting a collision between resourcesallocated to different channels. At 904, operations 900 continue byinitiating collision handling when processing the different channelsbased on the detection, wherein at least one of the detection or theprocessing is based on one or more characteristics of the differentchannels or the wireless device, and wherein the one or morecharacteristics comprise at least one of one or more numerologiesassociated with at least one of the different channels, a modulationorder of at least one of the different channels, coding rate of at leastone of the different channels, or one or more capabilities of thewireless device.

FIG. 10 illustrates example operations 1000 relating to collisionhandling in NR, according to aspects of the present disclosure.Operations 1000 may be performed, for example, by a UE or a basestation.

Operations 1000 begin, at 1002, by determining a size of a resourceblock group (RBG) based, at least in part, on a location of the RBGrelative to at least one of a synchronization channel, a physicalbroadcast channel (PBCH), or bandwidth edge. At 1004, operations 1000continue by determining allocated resources based on the determinedsize.

As discussed above, in some embodiments, for handling NR PDSCH/PDCCHcollisions with NR PSS/SSS/PBCH a set of factors may be considered. Theset of factors may include at least one of the numerologies associatedwith the PDSCH/PDCCH channels (with respect to the numerology associatedwith NR PSS/SSS/PBCH), the modulation order of the PDSCH/PDCCH channelsand/or the coding rate of the PDSCH/PDCCH channels, and the UE'scapability for interference or collision handling.

Under the first factor, as described above, whether PDSCH/PDCCH has thesame numerology as PSS/SSS/PBCH may, in some embodiments, be consideredin handling NR PDSCH/PDCCH collisions with NR PSS/SSS/PBCH. Thisnumerology dependency is illustrated by FIG. 11. As shown by diagram1110 of FIG. 11, where PDSCH/PDCCH has the same numerology asPSS/SSS/PBCH, the collision definition may be similar to that of LTE.That is, as long as the RBs for PDSCH/PDCCH and the RBs for PSS/SSS/PBCHoverlap, they may collide. However, in some cases, as shown by diagram1120 of FIG. 11, PDSCH/PDCCH may have a different numerology thanPSS/SSS/PBCH. In such embodiments, a collision may be detected if theRBs for PDSCH/PDCCH overlap or are within Δf (i.e., frequency gap) ofthe RBs of PSS/SSS/PBCH. In other words, due to different numerologies,PDSCH/PDCCH may be interfered by PSS/SSS/PBCH. In some embodiments, inorder to mitigate the impact of this interference, when processingPDSCH/PDCCH, the wireless device may assume that resources very close toPSS/SSS/PBCH in frequency are colliding (i.e., detect a collision) andthus skip such resources. In some embodiments, Δf can also be differentfor different combinations of numerologies (e.g., a first value for 15kHz vs. 30 kHz, a second value for 60 kHz vs. 30 kHz, etc.).

Under the second factor, as described above, the modulation order and/orthe coding rate of the PDSCH/PDCCH channels may be considered inhandling NR PDSCH/PDCCH collisions with NR PSS/SSS/PBCH, in someembodiments. In such embodiments, the size of the frequency gap (Δf) mayfurther be a function of modulation order and/or coding rates. Forexample, Δf may be 0 if modulation order satisfies or is below a certainthreshold and the coding rate is below a certain threshold. Forinstance, if the modulation order is quadrature phase-shifting keying(QPSK) and the coding rate is 0.8 or lower, then Δf=0. However, if themodulation order is, e.g., 16 quadrature amplitude modulation (QAM) andabove, or the coding rate is higher than e.g., 0.8, then Δf>0.

Under the third factor, as described above, a wireless device's or theUE's capability for interference handling (e.g., interferencemitigation, cancellation, and/or suppression capabilities) may beconsidered in handling NR PDSCH/PDCCH collisions with NR PSS/SSS/PBCH,in some embodiments. In such embodiments, the gap Δf may further be afunction of UE capability. It is important to note that different UEsmay have different interference handling capability, for example, due todifferent filtering operations. In addition, a UE may indicate itscapability under various operation conditions (e.g., as a function ofthe modulation and coding scheme (MCS)). For instance, UE1 may have Δf1,while UE2 may have Δf2 for the same set of conditions.

In some embodiments, handling NR PDSCH/PDCCH collisions with NRPSS/SSS/PBCH may depend on the RS type and RS locations. For widebandRS-based PDSCH (similar to CRS based PDSCH), handling collision may beperformed on a per-RE basis instead of on a per-RB basis. It isimportant to note that in LTE, in some cases, DM-RS collides withPSS/SSS/PBCH. In NR, however, DM-RS for PDSCH and/or PDCCH may befront-loaded, and, in some cases, may not be in the same symbol asPSS/SSS/PBCH. Accordingly, depending on RS locations, collision handlingmay be different. In some embodiments, if DM-RS for PDSCH does notcollide with PSS/SSS/PBCH in the same symbol, collision handling may bedone on a per RE basis. Also, even in embodiments where in an RB, PDSCHis colliding with PSS/SSS/PBCH, PDSCH may still use the REs in the RBthat are not colliding with PSS/SSS/PBCH. In some other embodiments,however, if DM-RS for PDSCH does collide with PSS/SSS/PBCH, the entireRB may be skipped (even if there are some REs in the RB not collidingwith PSS/SSS/PBCH).

Moving now to handling potential interference in UL, in someembodiments, PUCCH for a first UE may be of a first numerology, whilePUSCH for a second UE may be of a second numerology. In suchembodiments, the first UE and the second UE may be the same ordifferent. For example, a resource pool may be defined for PUCCH with afirst numerology. If a PUSCH is assigned with a different numerology, itmay interfere with (and be interfered by) PUCCH of the same UE or otherUEs. To handle such potential UL interferences, a gap of may be defined,in some embodiments. In such embodiments, the gap may also be a functionof numerology combinations, eNB processing capability, MCS, etc.

In some other embodiments, to alleviate resource allocation issues, RBGmay be non-uniformly defined depending on proximity with PSS/SSS/PBCHand/or bandwidth edge. As an example, for a 20 MHz bandwidth, assuming6-RB centered PSS/PSS/PBCH (in RBs 47, 48, 49, 50, 51, 52), instead ofdefining 25 RBGs each of 4 RBs, a 29 RBGs may be defined, where, RBG0(RBs 0-1 (2 RBs); RBG1: RBs 2-3); RBG2 (RBs 4-7 (4RBs), RBG3: RBs 8-11;RBG11: 40-43); RBG12 (44, 45; RBG13: 46, 47); RBG14 (48-51); RBG15(52-53; RBG16: 54-55); RBG17 (56-59; RBG18: 60-63; . . . ; RBG26:92-95); RBG2? (96, 97; RBG28: 98, 99). Such a non-uniform RBG definitionmay be enabled only in slots where there are PSS/SSS/PBCH or it may beenabled for all slots. In some embodiments, the RBG size is determinedbased on at least one of a time domain or frequency domain location ofthe RBG only for time intervals including at least one of asynchronization channel or PBCH. In some aspects, the RBG size isdetermined based on at least one of a time domain or frequency domainlocation of the RBG in each time interval.

The methods disclosed herein comprise one or more steps or actions forachieving the described method. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover a, b, c,a-b, a-c, b-c, and a-b-c, as well as any combination with multiples ofthe same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b,b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishingand the like.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed under the provisions of 35U.S.C. § 112, sixth paragraph, unless the element is expressly recitedusing the phrase “means for” or, in the case of a method claim, theelement is recited using the phrase “step for.”

The various operations of methods described above may be performed byany suitable means capable of performing the corresponding functions.The means may include various hardware and/or software component(s)and/or module(s), including, but not limited to a circuit, anapplication specific integrated circuit (ASIC), or processor. Generally,where there are operations illustrated in figures, those operations mayhave corresponding counterpart means-plus-function components withsimilar numbering.

For example, means for transmitting and/or means for receiving maycomprise one or more of a transmit processor 420, a TX MIMO processor430, a receive processor 438, or antenna(s) 434 of the base station 110and/or the transmit processor 464, a TX MIMO processor 466, a receiveprocessor 458, or antenna(s) 452 of the user equipment 120.Additionally, means for generating, means for multiplexing, and/or meansfor applying may comprise one or more processors, such as thecontroller/processor 440 of the base station 110 and/or thecontroller/processor 480 of the user equipment 120.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device (PLD),discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any commercially available processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in hardware, an example hardware configuration maycomprise a processing system in a wireless node. The processing systemmay be implemented with a bus architecture. The bus may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system and the overall design constraints.The bus may link together various circuits including a processor,machine-readable media, and a bus interface. The bus interface may beused to connect a network adapter, among other things, to the processingsystem via the bus. The network adapter may be used to implement thesignal processing functions of the PHY layer. In the case of a userterminal 120 (see FIG. 1), a user interface (e.g., keypad, display,mouse, joystick, etc.) may also be connected to the bus. The bus mayalso link various other circuits such as timing sources, peripherals,voltage regulators, power management circuits, and the like, which arewell known in the art, and therefore, will not be described any further.The processor may be implemented with one or more general-purpose and/orspecial-purpose processors. Examples include microprocessors,microcontrollers, DSP processors, and other circuitry that can executesoftware. Those skilled in the art will recognize how best to implementthe described functionality for the processing system depending on theparticular application and the overall design constraints imposed on theoverall system.

If implemented in software, the functions may be stored or transmittedover as one or more instructions or code on a computer readable medium.Software shall be construed broadly to mean instructions, data, or anycombination thereof, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. The processor may beresponsible for managing the bus and general processing, including theexecution of software modules stored on the machine-readable storagemedia. A computer-readable storage medium may be coupled to a processorsuch that the processor can read information from, and write informationto, the storage medium. In the alternative, the storage medium may beintegral to the processor. By way of example, the machine-readable mediamay include a transmission line, a carrier wave modulated by data,and/or a computer readable storage medium with instructions storedthereon separate from the wireless node, all of which may be accessed bythe processor through the bus interface. Alternatively, or in addition,the machine-readable media, or any portion thereof, may be integratedinto the processor, such as the case may be with cache and/or generalregister files. Examples of machine-readable storage media may include,by way of example, RAM (Random Access Memory), flash memory, ROM (ReadOnly Memory), PROM (Programmable Read-Only Memory), EPROM (ErasableProgrammable Read-Only Memory), EEPROM (Electrically ErasableProgrammable Read-Only Memory), registers, magnetic disks, opticaldisks, hard drives, or any other suitable storage medium, or anycombination thereof. The machine-readable media may be embodied in acomputer-program product.

A software module may comprise a single instruction, or manyinstructions, and may be distributed over several different codesegments, among different programs, and across multiple storage media.The computer-readable media may comprise a number of software modules.The software modules include instructions that, when executed by anapparatus such as a processor, cause the processing system to performvarious functions. The software modules may include a transmissionmodule and a receiving module. Each software module may reside in asingle storage device or be distributed across multiple storage devices.By way of example, a software module may be loaded into RAM from a harddrive when a triggering event occurs. During execution of the softwaremodule, the processor may load some of the instructions into cache toincrease access speed. One or more cache lines may then be loaded into ageneral register file for execution by the processor. When referring tothe functionality of a software module below, it will be understood thatsuch functionality is implemented by the processor when executinginstructions from that software module.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (DSL), or wireless technologies such as infrared(IR), radio, and microwave, then the coaxial cable, fiber optic cable,twisted pair, DSL, or wireless technologies such as infrared, radio, andmicrowave are included in the definition of medium. Disk and disc, asused herein, include compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Thus, in some aspects computer-readable media maycomprise non-transitory computer-readable media (e.g., tangible media).In addition, for other aspects computer-readable media may comprisetransitory computer-readable media (e.g., a signal). Combinations of theabove should also be included within the scope of computer-readablemedia.

Thus, certain aspects may comprise a computer program product forperforming the operations presented herein. For example, such a computerprogram product may comprise a computer-readable medium havinginstructions stored (and/or encoded) thereon, the instructions beingexecutable by one or more processors to perform the operations describedherein.

Further, it should be appreciated that modules and/or other appropriatemeans for performing the methods and techniques described herein can bedownloaded and/or otherwise obtained by a user terminal and/or basestation as applicable. For example, such a device can be coupled to aserver to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via storage means (e.g., RAM, ROM, a physical storage mediumsuch as a compact disc (CD) or floppy disk, etc.), such that a userterminal and/or base station can obtain the various methods uponcoupling or providing the storage means to the device. Moreover, anyother suitable technique for providing the methods and techniquesdescribed herein to a device can be utilized.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above without departingfrom the scope of the claims.

What is claimed is:
 1. A method for wireless communications by awireless device, comprising: receiving, at the wireless device,different downlink channels allocated to time and frequency resources;detecting a collision between resources allocated to the differentdownlink channels received at the wireless device, wherein the resourcesare the time and frequency resources allocated to the different downlinkchannels; and initiating collision handling when processing thedifferent downlink channels received at the wireless device based on thedetection, wherein: the collision handling comprises skipping processingof one or more portions of a first downlink channel that collide withone or more portions of a second downlink channel; at least one of thedetection or the processing is based on one or more characteristics ofthe different downlink channels or the wireless device; and the one ormore characteristics comprise at least one of one or more numerologiesassociated with at least one of the different downlink channels, amodulation order of at least one of the different downlink channels, ora coding rate of at least one of the different downlink channels.
 2. Themethod of claim 1, wherein the one or more numerologies includes a tonespacing.
 3. The method of claim 1, wherein: the different downlinkchannels comprise at least one of a physical downlink shared channel(PDSCH) or a physical downlink control channel (PDCCH) and at least oneof a synchronization channel or a physical broadcast channel (PBCH); andthe collision is detected if one or more resource blocks (RBs) allocatedto the PDCCH or PDSCH overlap with at least one of one or more resourceelements, RBs, RB groups allocated to the synchronization channel orPBCH.
 4. The method of claim 1, wherein: the different downlink channelscomprise at least one of a physical downlink shared channel (PDSCH) or aphysical downlink control channel (PDCCH) and at least one of asynchronization channel or a physical broadcast channel (PBCH); and thecollision is detected if one or more resource blocks (RBs) allocated tothe PDCCH or PDSCH overlap with, or are within a frequency gap of, oneor more RBs allocated to the synchronization channel or PBCH.
 5. Themethod of claim 4, wherein different respective combinations of the oneor more numerologies for the different downlink channels have differentsize frequency gaps.
 6. The method of claim 4, wherein a size of thefrequency gap is based on at least one of the modulation order or thecoding rate of the at least one of the different downlink channels. 7.The method of claim 6, wherein a size of the frequency gap is less thana threshold if at least one of: the modulation order or the coding rateis below a threshold.
 8. The method of claim 4, wherein a size of thefrequency gap depends on one or more capabilities of the wirelessdevice.
 9. The method of claim 1, wherein the collision handling dependson at least one of a type or location of a reference signal (RS) in oneof the different downlink channels.
 10. The method of claim 9, whereinthe collision handling is performed on a resource element (RE) basis forwideband RS based PDSCH, skipping only PDSCH REs that collide with atleast one of synchronization channel or PBCH REs.
 11. The method ofclaim 9, wherein the one or more characteristics of the differentdownlink channels or the wireless device includes an interferencemitigation capability of the wireless device.
 12. The method of claim 9,wherein the collision handling is performed on a resource element (RE)basis for DM-RS based PDSCH, skipping only PDSCH REs that collide withat least one of synchronization channel or PBCH REs.
 13. An apparatusfor wireless communications, comprising: means for receiving, at theapparatus, different downlink channels allocated to time and frequencyresources; means for detecting a collision between resources allocatedto the different downlink channels received at the apparatus, whereinthe resources are the time and frequency resources allocated to thedifferent downlink channels; and means for initiating collision handlingwhen processing the different downlink channels received at theapparatus based on the detection, wherein: the collision handlingcomprises skipping processing of one or more portions of a firstdownlink channel that collide with one or more portions of a seconddownlink channel; at least one of the detection or the processing isbased on one or more characteristics of the different downlink channelsor the apparatus; and the one or more characteristics comprise at leastone of one or more numerologies associated with at least one of thedifferent downlink channels, a modulation order of at least one of thedifferent downlink channels, or a coding rate of at least one of thedifferent downlink channels.
 14. The apparatus of claim 13, wherein theone or more numerologies includes a tone spacing.
 15. The apparatus ofclaim 14, wherein: the different downlink channels comprise at least oneof a physical downlink shared channel (PDSCH) or a physical downlinkcontrol channel (PDCCH) and at least one of a synchronization channel ora physical broadcast channel (PBCH); and the collision is detected ifone or more resource blocks (RBs) allocated to the PDCCH or PDSCHoverlap with at least one of one or more resource elements, RBs, RBgroups allocated to the synchronization channel or PBCH.
 16. Theapparatus of claim 14, wherein: the different downlink channels compriseat least one of a physical downlink shared channel (PDSCH) or a physicaldownlink control channel (PDCCH) and at least one of a synchronizationchannel or a physical broadcast channel (PBCH); and the collision isdetected if one or more resource blocks (RBs) allocated to the PDCCH orPDSCH overlap with, or are within a frequency gap of, one or more RBsallocated to the synchronization channel or PBCH.
 17. The apparatus ofclaim 16, wherein different respective combinations of the one or morenumerologies for the different downlink channels have different sizefrequency gaps.
 18. The apparatus of claim 17, wherein the collisionhandling is performed on a resource element (RE) basis for wideband RSbased PDSCH, skipping only PDSCH REs that collide with at least one ofsynchronization channel or PBCH REs.
 19. The apparatus of claim 17,wherein the one or more characteristics of the different downlinkchannels or the apparatus includes an interference mitigation capabilityof the apparatus.
 20. The apparatus of claim 16, wherein a size of thefrequency gap is based on at least one of the modulation order or thecoding rate of the at least one of the different downlink channels. 21.The apparatus of claim 14, wherein the collision handling depends on atleast one of a type or location of a reference signal (RS) in one of thedifferent downlink channels.